Coverage solution recommendation tool

ABSTRACT

A coverage solution recommendation tool may generate prioritized lists of coverage solutions for resolving a network coverage problem at a location. The tool may obtain network parameters of a wireless communication network that provides services to user devices at the location. The tool may further acquire device parameters of the user devices used at the location, as well as collect environment parameters associated with the location. The environment parameters may affect whether a wireless telecommunication carrier is able to leverage additional coverage solutions to provide services at the location. Accordingly, the coverage solution tool may generate a prioritized list of coverage solutions for resolving the network coverage problem based on the parameters.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of copending U.S. patent applicationSer. No. 14/849,036 filed Sep. 9, 2015 entitled “Coverage SolutionRecommendation Tool,” which is expressly incorporated herein byreference in its entirety.

BACKGROUND

Mobile devices are integral to the daily lives of most users. Wirelesscommunication devices are used to make voice calls, check email and textmessages, update social media pages, stream media, browse websites, andso forth. As a result, users of mobile devices expect a wirelesstelecommunication carrier to provide constant and reliabletelecommunication and data communication services at all times.

The reliability of telecommunication and data communication services maybe affected by multiple factors, such as geography and terrain, devicefeatures and capabilities, as well as network infrastructure and networkcoverage deployment. A wireless telecommunication carrier may offerdifferent coverage solutions to improve network coverage and increasenetwork reliability, but often such coverage solutions cannot be offeredin real time. For example, a user may call a customer servicerepresentative of a wireless telecommunication carrier with a report ofwith a network coverage problem. However, the customer servicerepresentative may have insufficient time or information to analyze theparticular factors and circumstances that are affecting the user inorder to recommend the appropriate coverage solution to the problemexperienced by the user.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 illustrates an example architecture for deploying a coveragesolution recommendation tool.

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that implement the coverage solutionrecommendation tool.

FIG. 3 is an illustrative user interface of a coverage solution enginethat provides a prioritized solution list for remedying network coverageissues based on multiple input parameters.

FIG. 4 is a flow diagram of an example process for generating aprioritized solution list for remedying network coverage issues based onmultiple input parameters.

FIG. 5 is a flow diagram of an example process for determining apriority order of coverage solution recommendations.

FIG. 6 is a flow diagram of an example process for determining theapplicability of Wi-Fi router based solutions to solve a networkcoverage problem.

FIG. 7 is a flow diagram of an example process for determining theapplicability of small network cell based solutions to solve a networkcoverage problem.

FIG. 8 is a flow diagram of an example process for determining theapplicability of signal booster based solutions to solve a networkcoverage problem.

FIG. 9 is a flow diagram of an example process for determining aneligibility of a user with respect to recommended solutions that remedynetwork coverage problems.

DETAILED DESCRIPTION

This disclosure is directed to techniques for using a coverage solutionrecommendation tool to recommend one or more coverage solutions thatremedy a network coverage problem with respect to a wirelesscommunication network. The network coverage problem may be experiencedby a particular subscriber at a specific geographical location. Thenetwork coverage problem may manifest itself as frequently droppedcalls, incomplete calls, slow data downloads or uploads, and/or othersymptoms. The recommended coverage solutions may include implementationof Wi-Fi calling, distribution of new Wi-Fi routers, selectiveinstallation of signal boosters, deployment of new small network cells,and/or so forth. The coverage solution recommendation tool may include adecision engine that selects one or more coverage solutions based oninput parameters associated with the nature of a coverage problem. Theinput parameters may include network parameters of the wirelesscommunication network, device parameters of one or more user devicesutilized by the subscriber, and environment parameters at geographicallocation of the subscriber. In some instances, operational parameters ofthe wireless telecommunication carrier that operates the wirelesstelecommunication network may also play a role. In various embodiments,the coverage solution recommendation tool may generate a prioritizedlist of coverage solutions that are applicable to the coverage problem.Accordingly, the prioritized list may provide the user with an optimalcoverage solution, as well as access to alternative coverage solutionsin the event the user elects to forego the optimal coverage solution.

In some embodiments, the coverage solution recommendation tool may beprovided to a customer service representative at the wirelesstelecommunication carrier. In such embodiments, the customer servicerepresentative may use the coverage solution recommendation tool toassist subscribers who are experiencing network coverage problems withobtaining the ideal coverage solution. However, in other embodiments,the coverage solution recommendation tool may be deployed as a web-basedapplication that is accessible to authorized subscribers of the wirelesstelecommunication carrier. In this way, the coverage solutionrecommendation tool may function as a self-help tool that enables theauthorized subscribers to explore different coverage solutions to theirnetwork coverage problems.

Accordingly, the coverage solution recommendation tool may generateprioritized lists of coverage solutions by taking into account multipleoperational considerations, network parameters and device features, aswell as environmental variables that are otherwise difficult for acustomer service representative to analyze in an expedient and coherentmanner. The use of the coverage solution recommendation tool may enablecustomer service representatives to quickly and easily provide coveragesolutions for network coverage problems experienced by subscribers.Thus, the coverage solution recommendation tool may reduce the durationsof customer service support calls, increase customer satisfaction andretention, and generate higher revenue for wireless telecommunicationcarriers. The techniques described herein may be implemented in a numberof ways. Example implementations are provided below with reference tothe following figures.

Example Network Architecture

FIG. 1 illustrates an example architecture 100 for deploying a coveragesolution recommendation tool. The architecture 100 may include acoverage solution engine 102. The coverage solution engine 102 mayexecute on one or more computing devices 104. The computing devices 104may include general purpose computers, such as desktop computers, tabletcomputers, laptop computers, servers, and so forth. However, in otherembodiments, the computing devices 104 may include smart phones, gameconsoles, or other electronic devices that are capable of receiveinputs, process the inputs, and generate output data. In variousembodiments, the computing devices 104 may be operated by a wirelesstelecommunication carrier or a third-party entity that is working withthe wireless telecommunication carrier.

The coverage solution engine 102 may provide one or more recommendedcoverage solutions 108 for remedying a network coverage problem. Thenetwork coverage problem may be experienced by a subscriber 110 at alocation 112 while using one or more user devices 114. The one or moreuser devices 114 may be experiencing the network coverage problem whileusing services provided by the wireless communication network 106. Invarious embodiments, each of the user devices 114 may be a smart phone,a feature phone, a tablet computer, or another type of communicationdevice. The location 112 may be a residential address, a businessaddress, a set of geographical coordinates, and/or the like. Therecommended coverage solutions 108 may include implementation of Wi-Ficalling, distribution of Wi-Fi routers, selective installation of signalboosters, deployment of small network cells, and/or so forth. Theimplementation of Wi-Fi calling for a user device may involveconfiguring the software applications that are installed on the userdevice to support Wi-Fi calling. The distribution of a Wi-Fi router mayinvolve the installation of a new Wi-Fi router or a replacement Wi-Firouter at a location with a connection to the Internet. The new Wi-Firouter may support Wi-Fi calling through Wi-Fi calling capable userdevices over an Internet connection at the location. In some instances,the coverage solution engine 102 may generate a prioritized list ofrecommended coverage solutions that are applicable to the coverageproblem.

In various embodiments, the coverage solution engine 102 may generatethe one or more recommend coverage solutions 108 for the networkcoverage problem at the location 112 based on network parameters 116,device parameters 118, environment parameters 120, and/or operationalparameters 122. The network parameters 116 may include parameters thataffect the deployment of telecommunication services by the wirelesstelecommunication carrier. For example, the network parameters 116 mayinclude the availability of spectrum licenses at the location 112, theavailability of a Public Safety Access Point (PSAP) for the location112, the types of telecommunication carrier network signals that coverthe location 112, and/or so forth.

The device parameters 118 may include features and specification of theone or more user devices used by the subscriber 110 that areexperiencing network coverage problems at the location 112. For example,the device parameters 118 may include whether a user device is capableof more than 2G telecommunication, whether a user device is a Long-TermEvolution (LTE)-compatible device, whether a user device is capable ofWi-Fi calling, and/or so forth. The environment parameters 120 mayinclude environmental variables that impact whether the wirelesstelecommunication carrier is able to leverage additional coveragesolutions to provide telecommunication or data communication services atthe location 112. For example, the environmental parameters may includewhether access to the Internet is available at the location 112, whetherthere is sufficient Wi-Fi coverage at the location 112, the presence orabsence of pre-existing deployed small network cells proximate to thelocation 112, and/or so forth. The operational parameters 122 mayinclude consideration that relate to the business operations of thetelecommunication carrier that operates the wireless communicationnetwork 106. For example, the operational parameters 122 may include theinventory quantities of devices that can be used to provide the coveragesolutions, the profit or cost savings generated from the deployment ofeach coverage solution, whether a particular version of such a devicemay be substitute by another version of the device, the technicallongevity of each coverage solution device, and/or so forth.

In various embodiments, the network parameters 116, the deviceparameters 118, the environment parameters 120, and the operationalparameters 122 may be processed by decision algorithms of the coveragesolution engine 102. In turn, the decision algorithms of the coveragesolution engine 102 may provide one or more recommended coveragesolutions 108 for remedying a network coverage problem that a subscriber110 is experiencing at a location 112.

Example Computing Device Components

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that implement the coverage solutionrecommendation tool. The computing devices 104 may include acommunication interface 202, one or more processors 204, memory 206, andhardware 208. The communication interface 202 may include wirelessand/or wired communication components that enable the server to transmitdata to and receive data from other networked devices. The hardware 208may include additional hardware interface, data communication, or datastorage hardware. For example, the hardware interfaces may include adata output device (e.g., visual display, audio speakers), and one ormore data input devices. The data input devices may include, but are notlimited to, combinations of one or more of keypads, keyboards, mousedevices, touch screens that accept gestures, microphones, voice orspeech recognition devices, and any other suitable devices.

The memory 206 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD), high-definition multimedia/data storage disks, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that can be used to store information for access by a computingdevice. In contrast, communication media may embody computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave, or other transmissionmechanism.

The processors 204 and the memory 206 of the computing devices 104 mayimplement an operating system 210 and the coverage solution engine 102.The operating system 210 may include components that enable thecomputing devices 104 to receive and transmit data via variousinterfaces (e.g., user controls, communication interface, and/or memoryinput/output devices), as well as process data using the processors 204to generate output. The operating system 210 may include a presentationcomponent that presents the output (e.g., display the data on anelectronic display, store the data in memory, transmit the data toanother electronic device, etc.). Additionally, the operating system 210may include other components that perform various additional functionsgenerally associated with an operating system.

The coverage solution engine 102 may include a data input module 212, adatabase interface module 214, a solution module 216, an eligibilitymodule 218, and a data output module 220. The modules may includeroutines, program instructions, objects, and/or data structures thatperform particular tasks or implement particular abstract data types.The memory 206 may also include a data store 222 that is used by thecoverage solution engine 102. In various embodiments, the coveragesolution engine 102 may be a standalone application or a web-basedapplication.

The data input module 212 may receive data that are inputted by a uservia application user interfaces. The application user interfaces may bepresented via the standalone application or a web browser executing on acomputing device. The data may include an identity of the subscriber, alocation at which the subscriber is experience network coverageproblems, the identity of each user device that the subscriber is usingat the location. In various embodiments, the location may be aresidential address, a business address, a set of geographicalcoordinates, and/or the like. The data may further include various otherparameters, such as at one or more of the device parameters 118 and oneor more of the environment parameters 120. For example, a user may inputwhether a user device is capable of more than 2G telecommunication,whether a user device is a LTE-compatible device, whether a user deviceis capable of Wi-Fi calling, whether access to the Internet is availableat the location 112, and/or forth.

The database interface module 214 may interface with one or more networkdatabases 224. The network databases may include an engineering databasewhere one or more network parameters 116 are stored. For example,information such as the availability of spectrum licenses at thelocation, the availability of a PSAP for the location, the type androbustness of telecommunication carrier network signals that cover thelocation may be obtained from the engineering database. The types of thetelecommunication carrier network signals may include Second Generation(2G), Personal Communication Service (PCS), Advanced Wireless Services(AWS), and/or so forth. Signal robustness may be quantified in amultitude of ways, such as via signal strength or signal quality. Signalstrength may be measured via received signal strength indicator (RSSI),reference signal received power (RSRP), received channel power indicator(RCPI), or other measurements. Signal quality may be measured throughenergy to interface ratio (ECIO), reference signal received quality(RSRQ), signal to interference-plus-noise ratio (SINR), or othermeasurements.

In various embodiments, the engineering database may also storeinformation on the locations of known network coverage problems, as wellas locations, identities, and description of coverage devices that havebeen deployed to solve the known network coverage problems.

The network databases 224 may also include a subscriber database. Thesubscriber database may store information regarding each subscriber,such as the subscriber 110. For example, the information stored for asubscriber may include subscriber contact information, such as addressesand phone numbers. The information may further include subscriberauthentication data, subscriber account information, subscriber paymentinformation, subscriber payment history, user devices that areassociated with the subscriber, and/or so forth. The subscriber accountinformation may indicate whether the subscriber is a prepaid subscriberor a postpaid subscriber. The subscriber payment history may indicatewhether the account of the subscriber is in good standing or delinquent,i.e., whether the subscriber is current on payments or failed to make apredetermined number of periodic payments. In some embodiments, thesubscriber database may also store information regarding any coveragedevices that have already been deployed to solve network coverageproblems reported by each subscriber.

The network databases 224 may also include one or more device databases.The device databases may store device information on the user devices ofthe subscribers that are serviced by the wireless communication network106. For example, the device information for a user device may includedata on device features, device hardware and software specifications,device network compatibility, device configuration information, and/orso forth. In various embodiments, the device databases may includedatabases that are maintained by the wireless telecommunication carrierthat operates the wireless communication network 106, databases that aremaintained by a third-party device manufacturer, device databases thatare maintained by a third-party device retailer, and/or so forth.

The solution module 216 may use decision algorithms to analyze the datathat are obtained by the data input module 212 and the databaseinterface module 214 with respect to a network coverage problem at aparticular location. Accordingly, the solution module 216 may generateone or more recommended coverage solutions for remedying the networkcoverage problem. In various embodiment, the recommended coveragesolutions may include implementation of Wi-Fi calling, distribution ofWi-Fi routers, selective installation of signal boosters, deployment ofnew small network cells, and/or so forth. In some embodiments, thesolution module 216 may present multiple coverage solutions in aprioritized list.

The coverage solutions in the prioritized list may be ranked accordingto one or more considerations. The considerations may include solutioneffectiveness. Accordingly, a coverage solution (e.g., deployment of asignal booster) that is more likely to be more effective at a locationthan another coverage solution (e.g., implementation of Wi-Fi calling)may be prioritized higher on the list. The consideration may furtherinclude technical applicability. In one instance, a coverage solutionmay involve deploying a coverage device that supports device featuresthat are available to a user device of a subscriber, as well as devicefeatures that are unavailable to the user device. However, the coveragedevice may nevertheless be ranked with a higher priority on the listthan another coverage device of a different coverage solution thatsolely supports device features that are currently available to the userdevice. This may be due to the fact that those unavailable devicefeatures are likely to become industry supported norms in the nearfuture. Alternative or concurrently, the currently supported devicefeatures may become obsolete within the predetermined time period. As aresult, the subscriber is likely to acquire user devices that willsupport these currently unavailable device features.

The considerations may additionally include business variables. In oneinstance, the wireless telecommunication carrier may have acquired aninventory of devices that may be deployed as a part of a first coveragesolution at a discounted rate. Such an inventory of devices may be lesscostly than another inventory of devices of an alternative butcomparable second coverage solution. However, because the first coveragesolution may be deployed with a less costly device, the solution module216 may prioritize the first coverage solution over the second coveragesolution in the prioritized list. Following the generation of coveragesolutions, the solution module 216 may initiate the eligibility module218 to determine whether the subscriber is eligible for the each of thecoverage solutions.

The eligibility module 218 may determine whether a subscriber iseligible for the selected coverage solution. In various embodiments, theeligibility module 218 may determine the eligibility of the subscriberbased on the account type and/or the payment history for the subscriber.For example, the eligibility module 218 may determine that thesubscriber is ineligible if the account of the subscriber is a prepaidaccount instead of a postpaid account. In another example, thesubscriber may be ineligible if the subscriber is delinquent in paymentsto the wireless telecommunication carrier for a predetermined amount oftime, such as several months in a row.

Alternatively concurrently, the eligibility module 218 may determine theeligibility of the subscriber based on the implementation history of thecoverage solutions. For example, if a coverage device of a coveragesolution (e.g., a Wi-Fi router) has already been deployed at a locationfor the subscriber, the eligibility module 218 may determine that thesubscriber is ineligible for another implementation of the same coveragesolution. In another example, the eligibility module 218 may determinethat a subscriber may be ineligible for a coverage solution if thecoverage solution is already implemented for another subscriber at alocation that is in proximity to the location of the subscriber. Forinstance, a small network cell (e.g., a femtocell, a picocell, etc.) mayhave already been deployed for another subscriber that lives in aneighboring residence to the residence of the subscriber. Since thedeployment of a two small network cell in a confined area may causemutual signal interference between the two cells, the eligibility module218 may determine that the subscriber is ineligible for the coveragesolution.

On the other hand, if the eligibility module 218 determines that asubscriber is eligible for a coverage solution, the eligibility module218 may inform the solution module 216. In turn, the solution module 216may display the coverage solution in an application user interface. Insome instances, following a selection of a coverage solution via theapplication user interface, the solution module 216 may initiate afulfillment of the coverage solution. The fulfillment may includechanging network settings, implement configuration changes to makespecific network and/or device features available to the subscriber,start a transaction process for the eventual delivery of a particularcoverage device to the subscriber, and/or so forth.

In alternative embodiments, the solution module 216 may use theeligibility module 218 to determine whether a subscriber is eligibilityfor each of the one or more coverage solutions that are tailored for thesubscriber following the presenting the solutions via an applicationuser interface. In such embodiments, rather than omitting thepresentation of a coverage solution for which the subscriber isineligible, the solution module 216 may present the ineligible coveragesolution in the application user interface with a reason or explanationfor the ineligibility. Accordingly, the ineligible solution is notselectable for fulfillment from the application user interface.

The data output module 220 may generate the various application userinterfaces that are configured to receive data inputs and displayinformation to a user. The application user interfaces may include userinterfaces that request user identification information, addressinformation, user device information, etc., as well as application userinterfaces that provide coverage solutions, pre-requisite conditions forcoverage solution deployment, and/or reasons for eligibility orineligibility.

The data store 222 may store information that are processed by thecoverage solution engine 102. The information may include networkparameters 116, device parameters 118, environment parameters 120, andoperational parameters 122. The information may further include thecoverage solution recommendations that are generated by the coveragesolution engine 102. Additional details regarding the functionalities ofthe coverage solution engine 102 are discussed in the context of FIGS.3-9. Thus, the coverage solution engine 102 may include other modulesthat perform the functionalities described in the context of thesefigures.

Example User Interface

FIG. 3 is an illustrative application user interface 300 of a coveragesolution engine that provides a prioritized solution list for remedyingnetwork coverage problems based on multiple input parameters. Theapplication user interface 300 may include a subscriber informationportion 302, a device information portion 304, a questionnaire portion306, and a solution portion 308.

The subscriber information portion 302 may display the identificationinformation of a subscriber. For example, the subscriber information mayinclude the name of the subscriber, account identification of thesubscriber, and an account type of the subscriber. The deviceinformation portion 304 may provide information on the one or more userdevices for which the subscriber is having network coverage problems.For example, the device information for a particular user device mayinclude a device name, device model and manufacturer information, deviceidentification information, and/or so forth. The device identificationinformation may include an International Mobile Station EquipmentIdentity (IMEI), Mobile Equipment Identifier (MEID), Integrated CircuitCard ID (ICCID), and/or Electronic Serial Number (ESN). In variousembodiments, the information in the subscriber information portion 302and the device information portion 304 may include information that ismanually inputted and/or retrieved from the network databases 224.

The questionnaire portion 306 may enable the input of the deviceparameters 118 and/or the environment parameters 120 into the coveragesolution engine 102. For example, the information may include an addressat which the subscriber is experience network coverage problems, whetherInternet, Wi-Fi, or a carrier signal is available at the address, and/orso forth. The solutions portion 308 may list the one or more coveragesolutions that are recommend for the subscriber. For each recommendcoverage solution, the solutions portion 308 may display a descriptionof the solution, an indication of whether the subscriber is eligible forthe solution, prerequisites for implementing the coverage solution,and/or devices that are excluded from using the coverage solution. In aninstance in which the subscriber is ineligible for a coverage solutionthat resolves the network coverage problem, the solutions portion 308may display one or more reasons for the ineligibility.

Example Processes

FIGS. 4-9 present illustrative processes 400-900 for using a coveragesolution recommendation tool to recommend one or more coverage solutionsthat remedy a network coverage problem. Each of the processes 400-900 isillustrated as a collection of blocks in a logical flow chart, whichrepresents a sequence of operations that can be implemented in hardware,software, or a combination thereof. In the context of software, theblocks represent computer-executable instructions that, when executed byone or more processors, perform the recited operations. Generally,computer-executable instructions may include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the process. Fordiscussion purposes, the processes 400-900 are described with referenceto the architecture 100 of FIG. 1.

FIG. 4 is a flow diagram of an example process 400 for generating aprioritized solution list for remedying network coverage problems basedon multiple input parameters. At block 402, the coverage solution engine102 may receive an indication that one or more user devices areexperiencing a network coverage problem at a location. The networkcoverage problem may result in an inability to use the one or more userdevices to complete calls, dropped calls, slow data download or upload,and/or so forth. The location may be a residential address, a businessaddress, a set of geographical coordinates, and/or the like.

At block 404, the coverage solution engine 102 may obtain at least onenetwork parameter of a wireless communication network that providesservices to the one or more user devices at the location. The servicesmay include telecommunication and data communication services. Invarious embodiments, the network parameters may include parameters thataffect the deployment of the services to the location by the wirelesstelecommunication carrier. For example, the network parameters mayinclude the availability of spectrum licenses at the location, theavailability of a PSAP for the location, the types of telecommunicationcarrier network signals that cover the location, and/or so forth.

At block 406, the coverage solution engine 102 may acquire at least onedevice parameter of one or more user devices at the location. The one ormore user devices may be experiencing a network coverage problem at thelocation. In various embodiments, the device parameters may includefeatures and specification of the one or more user devices. For example,the device parameters may include whether a user device is capable ofmore than 2G telecommunication, whether a user device is aLTE-compatible device, whether a user device is capable of Wi-Ficalling, and/or so forth.

At block 408, the coverage solution engine 102 may collect one or moreuser environment parameters associated with the location. Theenvironment parameters may include environmental variables that impactwhether the wireless telecommunication carrier is able to leverageadditional coverage solutions to provide telecommunication or datacommunication services at the location. For example, the environmentalparameters may include whether access to the Internet is available atthe location, whether there is sufficient Wi-Fi coverage at thelocation, the presence or absence of pre-existing deployed small networkcells proximate to the location, and/or so forth.

At block 410, the coverage solution engine 102 may receive one or moreoperational parameters of a wireless telecommunication carrier thatoperates the wireless communication network. The operational parametersmay include consideration that relate to the business operations of thetelecommunication carrier that operates the wireless communicationnetwork. For example, the operational parameters may include theinventory quantities of devices that can be used to provide the coveragesolutions, the profit or cost savings generated from the deployment ofeach coverage solution, whether a particular version of such a devicemay be substitute by another version of the device, the technicallongevity of each coverage solution device, and/or so forth.

At block 412, the coverage solution engine 102 may generate aprioritized list of one or more recommended coverage solutions forresolving the network coverage problem based on the parameters. Invarious embodiments, the prioritized list may provide the user with anoptimal coverage solution, as well as access to alternative coveragesolutions in the event the user elects to forego the optimal coveragesolution. In some alternative embodiments, the coverage solution engine102 may determine the prioritized list without receiving and using theone or more operational parameters of the wireless telecommunicationcarrier.

FIG. 5 is a flow diagram of an example process 500 for determining apriority order of coverage solution recommendations. The process 500 mayfurther illustrate the block 412 of the process 400. At block 502, thesolution module 216 may identify a subscriber of a wireless carriernetwork. The solution module 216 may identify subscriber the based oninformation received from the subscriber, such as a name, Mobile StationInternational Subscriber Directory Number (MSISDN), an account number, apassword, a personal identification number (PIN), and/or otherauthentication credentials.

At block 504, the solution module 216 present one or more locations(e.g., addresses) that are associated with an account of the subscriber.The one or more locations may be presented via an application userinterface of the solution module 216. In various embodiments, thesolution module 216 may retrieve the location information from asubscriber database. At block 506, the solution module 216 may receive aselection of a location that is inputted via the application userinterface. The selection of the location may be inputted into thesolution module 216 by a subscriber or a customer service representativethat is assisting the subscriber. In alternative embodiments, thesolution module 216 may receive a direct input of a location that issupplied by a subscriber instead of a selection of a location that isassociated with the account of the subscriber.

At decision block 508, the solution module 216 may validate thelocation. In various embodiments, the validation may be performed toensure that the location is for a location that is serviced by thewireless communication network 106. Thus, if the solution module 216determines that the location is invalid (“no” at decision block 508),the process 500 may loop back to block 506 so that another location maybe selected or inputted. However, if the solution module 216 determinesthat the location is valid (“yes” at decision block 508), the process500 may proceed to block 510.

At block 510, the solution module 216 may present one or more userdevices that are associated with the account of the subscriber. The oneor more user devices may be presented via an application user interfaceof the solution module 216. Each user device may be configured to usethe telecommunication and/or data communication services that areprovided by the wireless communication network 106. The solution module216 may retrieve the information regarding each of the user devices froma device database that is accessible to the solution module 216. Atblock 512, the solution module 216 may receive a selection of one ormore user devices. The selection may be received via the applicationuser interface of the solution module 216.

At decision block 514, the solution module 216 may determine whetherthere is Internet availability at the location. Accordingly, if there isno Internet at the location (“no” at decision block 514), the process400 may proceed to block 516. At block 516, the solution module 216 maydetermine that Wi-Fi calling is not available as a coverage solution forthe location.

However, if there is Internet at the location (“yes” at decision block514), the process 500 may continue to decision block 518. At decisionblock 518, the solution module 216 may determine whether there issufficient Wi-Fi coverage at the location. In some embodiments, thesufficiency of the Wi-Fi coverage may be a subjective measurement. Forexample, the subscriber may be queried as to whether there is “good”Wi-Fi coverage at the location. If the answer is there is “good” Wi-Fi,then an indication of the sufficient Wi-Fi coverage may be inputted intothe solution module 216.

In other embodiments, the sufficiency of the Wi-Fi coverage may be anobjective measure. For example, the subscriber may be queried as towhether the Wi-Fi signal that provides the Wi-Fi coverage at thelocation meets a predetermined signal strength, a predetermined signalquality threshold, or supports a predetermined download and/or uploadspeed. If the answer is that the Wi-Fi signal meets a predeterminedsignal strength, a predetermined signal quality threshold, or supports apredetermined download and/or upload speed, then an indication of thesufficient Wi-Fi coverage may be inputted into the solution module 216.Thus, at decision block 518, if the solution module 216 determines thatthere is insufficient Wi-Fi coverage at the location (“no” at decisionblock 518), the process 500 may once again proceed to block 516. Oncethe solution module 216 determines that Wi-Fi calling is not availableas a coverage solution for the location, the process 500 may proceed todecision block 520. However, if the solution module 216 determines thatthere is sufficient Wi-Fi coverage at the location (“yes” at decisionblock 518), the process 500 may proceed directly to decision block 520.

At decision block 520, the solution module 216 may determine whetherthere is a carrier signal of the wireless communication network 106 atthe location. The availability of the carrier signal may be determinedbased on data from an engineering database. In various embodiments, thesolution module 216 may determine that a carrier signal is available ifthe signal robustness of the carrier signal is above a predeterminedrobustness threshold at the location. Thus, at decision block 520, ifthe solution module 216 determines that the carrier signal is availableat the location (“yes” at decision block 520), the process 500 mayproceed to block 522. At block 522, the solution module 216 may checkfor PSAP availability at the location. The availability of the PSAPmeans that the emergency services may be automatically informed of thelocation if an emergency service call is initiated using a user deviceat or in the vicinity of the location. The availability of the PSAP maybe a regulatory prerequisite for the deployment of some coveragesolutions at the location.

At block 524, the solution module 216 may determine whether a PCSspectrum is available at the location. The availability of the PCSspectrum may be dependent on whether the wireless telecommunicationcarrier that operates the wireless communication network 106 has agovernment issued license to deploy the PCS spectrum in a region thatencompasses the location. Accordingly, the solution module 216 maydetermine that the PCS spectrum is unavailable if the wirelesstelecommunication carrier has no government issued license to deploy thePCS spectrum. In various embodiments, the solution module 216 may makethe determination based on data retrieved from an engineering database.

At block 526, the solution module 216 may determine whether an AWSspectrum is available at the location. The availability of the AWSspectrum may be dependent on whether the wireless telecommunicationcarrier that operates the wireless communication network 106 has agovernment issued license to deploy the AWS spectrum in a region thatencompasses the location. Accordingly, the solution module 216 maydetermine that the AWS spectrum is unavailable if the wirelesstelecommunication carrier has no government issued license to deploy theAWS spectrum. In various embodiments, the solution module 216 may makethe determination based on data retrieved from an engineering database.

At block 528, the solution module 216 may check for the signal type ofthe carrier signal at the location. Accordingly, the solution module 216may determine whether the carrier signal is a 2G signal, a PCS signal,an AWS signal, and/or so forth. In various embodiments, the solutionmodule 216 may make the determination based on data retrieved from anengineering database. The type of the carrier signal may affect whethersome coverage solutions are available at the location.

At block 530, the solution module 216 may determine a prioritized listof one or more coverage solutions for resolving the network coverageproblem at the location. In various embodiments, the recommendedcoverage solutions may include implementation of Wi-Fi calling,distribution of new Wi-Fi routers, selective installation of signalboosters, deployment of new small network cells, and/or so forth.Returning to decision block 520, if the solution module 216 determinesthat the carrier signal is not available at the location (“no” atdecision block 520), the process 500 may proceed to block 532. At block532, the solution module 216 may determine that no coverage solution forresolving the network coverage problem at the location is available.

FIG. 6 is a flow diagram of an example process 600 for determining theapplicability of Wi-Fi router based solutions to solve a networkcoverage problem. The process 600 may further illustrate the block 530of the process 500. At block 602, the solution module 216 may receivedata associate with one or more user devices at a location (e.g., anaddress). The one or more user devices may be experiencing a networkcoverage problem at the location. In various embodiments, the data mayinclude network parameters 116, device parameters 118, and environmentparameters 120.

At decision block 604, the solution module 216 may determine whether theInternet available at the location. According, if the Internet isavailable at the location (“yes” at decision block 604), the process 600may proceed to decision block 606. At decision block 606, the solutionmodule 216 may determine whether at least one Wi-Fi calling capable userdevice is used at the location. Thus, if at least one Wi-Fi callingcapable user device is used at the location (“yes” at decision block606), the process 600 may proceed to block 608.

At block 608, the solution module 216 may assess a sufficiency of Wi-Fiat the location. In various embodiments, the sufficiency of the Wi-Fimay be assessed on a subjective or objective basis. For example, thesubscriber may be queried as to whether there is “good” Wi-Fi coverageat the location. The subjective standard of “good” being used as apredetermined threshold. In another example, the subscriber may bequeried as to whether the Wi-Fi signal that provides the Wi-Fi coverageat the location meets a predetermined signal strength, a predeterminedsignal quality threshold, or a predetermined upload and/or downloadspeed threshold. Thus, at decision block 610, if the solution module 216determines that the Wi-Fi sufficiency meets a predetermined threshold(“yes” at decision block 610), the process 600 may proceed to block 612.At block 612, the solution module 216 may make a recommendation ofcoverage solutions that includes the prioritization of an implementationof Wi-Fi calling at the location over an installation of a Wi-Fi routerat the location.

However, if the solution module 216 determines that the Wi-Fisufficiency does not meet a predetermined threshold (“no” at decisionblock 610), the process 600 may proceed to block 614. At block 614, thesolution module 216 may recommend coverage solutions that includes theprioritization of the installation of a Wi-Fi router at the locationover the implementation of Wi-Fi calling at the location.

Returning to decision block 604, if the Internet is unavailable at thelocation (“no” at decision block 604), the process 600 may proceed toblock 616. At block 616, the solution module 216 may determine that theno coverage solution that involves Wi-Fi calling or Wi-Fi routerinstallation is applicable. Likewise, returning to decision block 606,if the solution module 216 determine that no Wi-Fi calling capable userdevice is used at the location (“yes” at decision block 606), theprocess 600 may also proceed to block 616.

FIG. 7 is a flow diagram of an example process 700 for determining theapplicability of small network cell based solutions to solve a networkcoverage problem. The process 700 may further illustrate the block 530of the process 500. At block 702, the solution module 216 may receivedata associate with one or more user devices at a location (e.g., anaddress). The one or more user devices may be experiencing a networkcoverage problem at the location. In various embodiments, the data mayinclude network parameters 116, device parameters 118, and environmentparameters 120.

At decision block 704, the solution module 216 may determine whether theInternet available at the location. According, if the Internet isavailable at the location (“yes” at decision block 704), the process 700may proceed to decision block 706. At decision block 706, the solutionmodule 216 may determine whether all of the one or more user devices areno more than 2G capable. In various embodiments, the solution module 216may make the determination based on data retrieved from a devicedatabase. Accordingly, if the solution module 216 determines that atleast one of the user devices is more than 2G capable (“no” at decisionblock 706), the process 700 may proceed to decision block 708.

At decision block 708, the solution module 216 may determine whetherPSAP is available at the location. In various embodiments, theavailability of the PSAP means that the emergency services may beautomatically informed of the location if an emergency service call isinitiated using a user device at or in the vicinity of the location. Thesolution module 216 may make the determination based on data retrievedfrom an engineering database. Thus, if the solution module 216determines that PSAP is available at the location (“yes” at decisionblock 708), the process 700 may proceed to decision block 710.

At decision block 710, the solution module 216 may determine whether PCSand AWS spectrums are available at the location. In various embodiments,the availability of a spectrum may be dependent on whether the wirelesstelecommunication carrier that operates the wireless communicationnetwork 106 has a government issued license to deploy the spectrum in aregion that encompasses the location. Accordingly, if the solutionmodule 216 determines that PCS and AWS spectrums are available at thelocation (“yes” at decision block 710), the process 700 may continue todecision block 712.

At decision block 712, the solution module 216 may determine whether allof the one or more user devices are LTE-capable devices. Thus, if theall of the user devices are LTE-capable (“yes” at decision block 712),the process 700 may proceed to block 714. At block 714, the solutionmodule 216 may make a recommendation to install a LTE/Universal MobileTelecommunications System (UMTS)-capable small network cell at thelocation. However, if not all of the user devices are LTE-capable (“no”at decision block 712), the process 700 may proceed to block 716. Atblock 716, the solution module 216 may make a recommendation to installan UMTS-capable small network cell at the location.

Returning to decision block 704, if the Internet is unavailable at thelocation (“no” at decision block 704), the process 700 may proceed toblock 718. At block 718, the solution module 216 may determine that nocoverage solution involving small network cell is applicable inresolving the network coverage problem at the location. Returning todecision block 706, if the solution module 216 determines that all ofthe user devices are no more than 2G capable, (“yes” at decision block706), the process 700 may proceed directly to block 718. Returning todecision block 708, if the solution module 216 determines that PSAP isunavailable at the location (“no” at decision block 708), the process700 may proceed directly to block 718. Likewise, returning to decisionblock 710, if the solution module 216 determines that PCS and AWSspectrums are unavailable at the location (“no” at decision block 710),the process 700 may proceed directly to block 718.

FIG. 8 is a flow diagram of an example process 800 for determining theapplicability of signal booster based solutions to solve a networkcoverage problem. The process 800 may further illustrate the block 530of the process 500. At block 802, the solution module 216 may receivedata associate with one or more user devices at a location (e.g., anaddress). The one or more user devices may be experiencing a networkcoverage problem at the location. In various embodiments, the data mayinclude network parameters 116, device parameters 118, and environmentparameters 120.

At decision block 804, the solution module 216 may determine whether atleast one bar of carrier signal is available at the location. In someembodiments, the solution module 216 may make the determination based onnetwork coverage data from an engineering database. In otherembodiments, the solution module 216 may use an input from a user tomake the determination. Accordingly, if the solution module 216determines that at least one bar of carrier signal is available at thelocation (“yes” at decision block 804), the process 800 may proceed todecision block 806.

At decision block 806, the solution module 216 may determine whether allof the one or more user devices are no more than 2G capable. Thesolution module 216 may make the determination based on data retrievedfrom a device database. Accordingly, if at least one of the user devicesis more than 2G capable (“no” at decision block 806), the process 800may proceed to decision block 808.

At decision block 808, the solution module 216 may determine whether anUMTS signal is available at the location. The solution module 216 maymake the determination based on data retrieved from the engineeringdatabase. Accordingly, if the UMTS signal is available at the location(“yes” at decision block 808), the process 800 may proceed to decisionblock 810. At decision block 810, the solution module 216 may determinewhether a LTE signal is available at the location. The solution module216 may make the determination based on data retrieved from theengineering database. Accordingly, if the LTE signal is unavailable atthe location (“no” at decision block 810), the process may proceed toblock 812. At block 812, the solution module 216 may make arecommendation that prioritizes the installation an LTE-compatiblesignal booster over a LTE non-compatible signal booster.

Returning to decision block 808, if the UMTS signal is unavailable atthe location (“no” at decision block 808), the process 800 may proceedto decision block 814. At decision block 814, the solution module 216may determine whether a LTE signal is available at the location. Thesolution module 216 may make the determination based on data retrievedfrom the engineering database. Accordingly, if the LTE signal isavailable at the location (“yes” at decision block 814), the process mayproceed to decision block 816.

At decision block 816, the solution module 216 may determine whetherVoice over LTE (VoLTE) is available at the location. The solution module216 may make the determination based on data retrieved from theengineering database. Accordingly, if the solution module 216 determinesthat VoLTE is available at the location (“yes” at decision block 816),the process 800 may proceed to decision block 818.

At decision block 818, the solution module 216 may determine whether atleast one VoLTE user device is being used at the location. The solutionmodule 216 may make the determination based on data retrieved from adevice database. Accordingly, if at least one VoLTE-capable user deviceis used at the location (“yes” at decision block 818), the process 800may proceed to block 820. At block 820, the solution module 216 may makea recommendation to install a LTE-compatible signal booster at thelocation.

Returning to decision block 810, if the LTE signal is available at thelocation (“yes” at decision block 810), the process may proceed todecision block 822. At decision block 822, the solution module 216 maydetermine whether at least one LTE-capable user device is being used atthe location. The solution module 216 may make the determination basedon data retrieved from a device database. Accordingly, if at least oneLTE-capable user device is used at the location (“yes” at decision block822), the process 800 may proceed to block 820. However, if noLTE-capable user device is used at the location (“no” at decision block822), the process 800 may proceed to block 812.

Returning to decision block 804, if the solution module 216 determinesthat no bars of carrier signal is available at the location (“no” atdecision block 804), the process 800 may proceed to block 824. At block824, the solution module 216 may determine that no coverage solutioninvolving a signal booster is applicable. Likewise, returning todecision block 806, if all of the user devices are no more than 2Gcapable (“yes” at decision block 806), the process 800 may once againproceed to block 824.

Returning to decision block 814, if the LTE signal is unavailable at thelocation (“no” at decision block 814), the process may proceed to block824. Further, returning to decision block 816, if the solution module216 determines that VoLTE is unavailable at the location (“no” atdecision block 816), the process 800 may also proceed block 824.Likewise, returning to decision block 818, if no VoLTE-capable userdevice is used at the location (“no” at decision block 818), the process800 may further proceed to block 824.

FIG. 9 is a flow diagram of an example process 900 for determining aneligibility of a user with respect to recommended solutions that remedynetwork coverage problems. At block 902, the coverage solution engine102 may determine a coverage solution for resolving a network coverageproblem at a location (e.g., an address). In various embodiments, thecoverage solution may be determined by the solution module 216 of thecoverage solution engine 102. The coverage solution may include theconfiguration of a software application on a user device, or thedeployment of a solution device (e.g., a signal booster, a replace Wi-Firouter, etc.).

At decision block 804, the eligibility module 218 may determine whetherthe account of the user was identified. In various embodiments, theidentification of the account may include the user provide one or moreauthentication credentials for authenticating that the user isassociated with the account. According, if the user account isidentified (“yes” at decision block 904), the process 900 may proceed todecision block 906.

At decision block 906, the eligibility module 218 may determine whetherthe account of the user is a postpaid account. The eligibility module218 may make the determination based on data retrieved from thesubscriber database. In various embodiments, only a user with a postpaidaccount is eligible for a coverage solution that is recommended by thecoverage solution engine 102. Accordingly, if the eligibility module 218determines that the user account is a postpaid account (“yes” atdecision block 906), the process 900 may proceed to decision block 908.

At decision block 908, the eligibility module 218 may determine whetherthe recommended solution is already implemented for the location. Theeligibility module 218 may make the determination based on dataretrieved from the subscriber database. For example, the subscriber mayalready have a signal booster deployed at the location. In anotherexample, the subscriber may already have Wi-Fi calling implemented ontheir user device. Accordingly, if the recommended solution has not yetbeen implemented for the location (“no” at decision block 908), theprocess 900 may proceed to decision block 910.

At decision block 910, the eligibility module 218 may determine whetherthe recommend coverage solution is available for use at the location.The eligibility module 218 may make the determination based on dataretrieved from the subscriber database. For example, a neighboringlocation may already have a small network cell deployed to resolve acorresponding network coverage problem. Since the deployment of anothersmall network cell may cause signal interference, the eligibility module218 may determine that the recommended coverage solution is unavailablefor use. Accordingly, if the recommend coverage solution is availablefor use at the location (“yes” at decision block 910), the process 900may proceed to decision block 912.

At decision block 912, the eligibility module 218 may determine whetherthe account of the subscriber is delinquent. The eligibility module 218may make the determination based on data retrieved from the subscriberdatabase. Accordingly, if the account of the subscriber is notdelinquent (“no” at decision block 912), the process 900 may proceed toblock 914. At block 914, the coverage solution engine 102 may determinethat the subscriber is eligible for the coverage solution. Accordingly,the coverage solution engine 102 may present the coverage solution tothe subscriber for selection. In various embodiments, the coveragesolution may be presented via an application user interface that isgenerated by the coverage solution engine 102. A selection of thecoverage solution may cause the coverage solution engine 102 to initiatea fulfillment of the coverage solution. For example, the fulfillment mayinclude the initiation of a software application modification on a userdevice or shipment of a solution device (e.g., signal booster) to thesubscriber for installation at the location.

Returning to decision block 904, if the user account is not identified(“no” at decision block 904), the process 900 may proceed to block 916.At block 916, the eligibility module 218 of the coverage solution engine102 may determine that the subscriber is ineligible for the coveragesolution. Returning to decision block 906, if the user account is not apostpaid account (“no” at decision block 906), the process 900 mayproceed to block 916. Returning to decision block 908, if therecommended solution is already implemented for the location (“yes” atdecision block 908), the process 900 may proceed to block 916. Returningto decision block 910, if the solution is unavailable for use (“no” atdecision block 910), the process 900 may proceed to block 916. Returningto decision block 912, if the account of the subscriber is delinquent(“yes” at decision block 912), the process 900 may also proceed to block916.

The coverage solution recommendation tool may generate prioritized listsof coverage solutions by taking into account multiple operationalconsiderations, network parameters and device features, as well asenvironmental variables that are otherwise difficult for a customerservice representative to analyze in an expedient and coherent manner.The use of the coverage solution recommendation tool may enable customerservice representatives to quickly and easily provide coverage solutionsfor network coverage problems experienced by subscribers. Thus, thecoverage solution recommendation tool may reduce the durations ofcustomer service support calls, increase customer satisfaction andretention, and generate higher revenue for wireless telecommunicationcarriers.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. One or more non-transitory computer-readablemedia storing computer-executable instructions that upon execution causeone or more processors to perform acts comprising: collecting one ormore environment parameters associated with a location at which one ormore user devices experienced a network coverage problem, the one ormore environment parameters affecting whether a wirelesstelecommunication carrier that provides services to the one or more userdevices at the location is able to leverage additional coveragesolutions to provide the services at the location; receiving a list ofone or more coverage solutions, at least one coverage solution of thelist comprises implementing Wi-Fi calling for the one or more userdevices and an installation of a Wi-Fi router that supports Wi-Ficalling at the location; and prioritizing the list of one or morecoverage solutions to generate a prioritized list of one or morecoverage solutions for resolving the network coverage problem at thelocation based at least on a plurality of parameters, wherein theplurality of parameters include at least one network parameter of thewireless telecommunication carrier at the location, at least one deviceparameter of the one or more user devices used at the location, and theone or more environment parameters, and wherein at least one of the oneor more coverage solutions provides additional network coverage to theone or more user devices utilizing unlicensed spectrum.
 2. The one ormore non-transitory computer-readable media of claim 1, wherein the actsfurther comprise receiving one or more operational considerations of thewireless telecommunication carrier, and wherein the plurality ofparameters further includes the operational considerations of thewireless telecommunication carrier.
 3. The one or more non-transitorycomputer-readable media of claim 2, wherein the one or more operationalconsiderations include an inventory quantity of a device for providing acoverage solution, a profit or a cost savings generated from adeployment of the coverage solution, whether a particular version of thedevice is interchangeable with another version of the device, or atechnical longevity of the device.
 4. The one or more non-transitorycomputer-readable media of claim 1, wherein the acts further comprisedetermining that a subscriber associated with the one or more userdevices is eligible for the one or more coverage solutions in responseto one or more conditions being satisfied, the one or more conditionsincluding that an account of the subscriber is a postpaid account, theaccount of the subscriber is non-delinquent, the one or more coveragesolutions are available for use at the location, and the one or morecoverage solutions are not previously implemented for the location. 5.The one or more non-transitory computer-readable media of claim 4,wherein a coverage solution in a form of a deployment of a small networkcell is available for use at the location when no pre-existing smallnetwork cell is deployed for a different subscriber at another locationthat is within a predetermined distance of the location.
 6. The one ormore non-transitory computer-readable media of claim 1, wherein the oneor more coverage solutions further include an installation of a signalbooster at the location, or a deployment of a small network cell at thelocation.
 7. The one or more non-transitory computer-readable media ofclaim 1, wherein the at least one network parameter includes anavailability of one or more spectrum licenses at the location, anavailability of a public-safety access point (PSAP) for the location, ora type of telecommunication carrier network signal that cover thelocation.
 8. The one or more non-transitory computer-readable media ofclaim 1, wherein the at least one device parameter includes whether auser device is capable of more than Second Generation (2G)telecommunication, whether the user device is a Long-Term Evolution(LTE)-compatible device, or whether the user device is capable of Wi-Ficalling.
 9. The one or more non-transitory computer-readable media ofclaim 1, wherein the one or more environment parameters include whetherInternet access is available at the location, whether a sufficiency ofWi-Fi coverage at the location meets a predetermined sufficiencythreshold, or whether a pre-existing deployed small network cell ispresent proximate to the location.
 10. The one or more non-transitorycomputer-readable media of claim 1, wherein the generating includesprioritizing an implementation of Wi-Fi calling for the one or more userdevices over an installation of a Wi-Fi router that supports Wi-Ficalling at the location in response to a sufficiency of Wi-Fi coverageat the location meeting a predetermined sufficiency threshold, orprioritizing the installation of the Wi-Fi router over theimplementation of Wi-Fi calling in response to the sufficiency of Wi-Ficoverage failing to meet the predetermined sufficiency threshold. 11.The one or more non-transitory computer-readable media of claim 1,wherein the generating includes recommending an installation of aLong-Term Evolution (LTE)/Universal Mobile Telecommunications System(UMTS)-capable small network cell at the location at least in responseto a determination that each of the one or more user devices areLTE-capable user devices, or recommending an installation of aUMTS-capable small network cell at the location at least in response toa determination that at least one of the one or more user devices is nota LTE-capable user device.
 12. The one or more non-transitorycomputer-readable media of claim 1, wherein the generating includesrecommending an installation of a Long-Term Evolution (LTE)-compatiblesignal booster at the location at least in response to a determinationthat at least one of the one or more user devices is a LTE-capable userdevice or a Voice over LTE (VoLTE)-capable user device, prioritizing aninstallation of a LTE-compatible signal booster over an installation ofa LTE non-compatible signal booster at least in response to adetermination that none of the one or more user devices is a LTE-capableuser device, or determining that no coverage solution involving a signalbooster is applicable at least in response to a determination that noneof the one or more user devices is a VoLTE-capable device.
 13. Acomputer-implemented method, comprising: collecting one or moreenvironment parameters associated with a location at which one or moreuser devices experienced a network coverage problem, the one or moreenvironment parameters affecting whether a wireless telecommunicationcarrier that provides services to the one or more user devices is ableto leverage additional coverage solutions to provide the services at thelocation; receiving one or more operational parameters of the wirelesstelecommunication carrier; receiving a list of one or more coveragesolutions, at least one coverage solution of the list comprisesimplementing Wi-Fi calling for the one or more user devices and aninstallation of a Wi-Fi router that supports Wi-Fi calling at thelocation; and prioritizing the list of one or more coverage solutions togenerate a prioritized list of one or more recommended coveragesolutions for resolving the network coverage problem at the locationbased at least on a plurality of parameters, wherein the plurality ofparameters include at least one of the at least one network parameter ofthe wireless telecommunication carrier at the location, at least onedevice parameter of the one or more user devices used at the location,the one or more environment parameters, or the one or more operationalparameters, and wherein at least one of the one or more recommendedcoverage solutions provides additional network coverage to the one ormore user devices utilizing unlicensed spectrum.
 14. Thecomputer-implemented method of claim 13, further comprising determiningthat a subscriber associated with the one or more user devices iseligible for the one or more recommended coverage solutions in responseto one or more conditions being satisfied, the one or more conditionsincluding that an account of the subscriber is a postpaid account, theaccount of the subscriber is non-delinquent, the one or more recommendedcoverage solutions are available for use at the location, and the one ormore recommended coverage solutions are not previously implemented forthe location.
 15. The computer-implemented method of claim 13, whereinthe one or more recommended coverage solutions further include aninstallation of a signal booster at the location, or a deployment of asmall network cell at the location.
 16. The computer-implemented methodof claim 13, wherein the at least one network parameter includes anavailability of one or more spectrum licenses at the location, anavailability of a public-safety access point (PSAP) for the location, ora type of telecommunication carrier network signal that cover thelocation.
 17. The computer-implemented method of claim 13, wherein theat least one device parameter includes whether a user device is capableof more than Second Generation (2G) telecommunication, whether the userdevice is a Long-Term Evolution (LTE)-compatible device, or whether theuser device is capable of Wi-Fi calling.
 18. The computer-implementedmethod of claim 13, wherein the one or more environment parametersinclude whether Internet access is available at the location, whether asufficiency of Wi-Fi coverage at the location meets a predeterminedsufficiency threshold, or whether a pre-existing deployed small networkcell is present proximate to the location.
 19. The computer-implementedmethod of claim 13, wherein the one or more operational parametersinclude an inventory quantity of a device for providing a coveragesolution, a profit or a cost savings generated from a deployment of thecoverage solution, whether a particular version of the device isinterchangeable with another version of the device, or a technicallongevity of the device.
 20. A system, comprising: one or moreprocessors; and memory including a plurality of computer-executablecomponents that are executable by the one or more processors to performa plurality of actions, the plurality of actions comprising: receiving alist of one or more coverage solutions at a location, at least onecoverage solution of the list comprising implementing Wi-Fi calling forone or more user devices that experienced a network coverage problem atthe location and an installation of a Wi-Fi router that supports Wi-Ficalling at the location; prioritizing the list of one or more coveragesolutions to generate a prioritized list of one or more coveragesolutions for resolving the network coverage problem at the locationbased at least on a plurality of parameters, wherein the plurality ofparameters include at least one network parameter of a wirelesstelecommunication carrier at the location, at least one device parameterof the one or more user devices used at the location, and one or moreenvironment parameters associated with the location, the one or moreenvironment parameters affecting whether the wireless telecommunicationcarrier is able to leverage additional coverage solutions to provideservices at the location, and wherein at least one of the one or morecoverage solutions provides additional network coverage to the one ormore user devices utilizing unlicensed spectrum; and determining that asubscriber associated with the one or more user devices is eligible forthe one or more coverage solutions in response to one or more conditionsbeing satisfied, the one or more conditions including that an account ofthe subscriber is a postpaid account, the account of the subscriber isnon-delinquent, the one or more coverage solutions are available for useat the location, and the one or more coverage solutions are notpreviously implemented for the location.